Some Macs recently received a macOS system update which disabled the simulator runtimes used by Xcode 15, including the simulators for iOS, tvOS, watchOS, and visionOS. If your Mac received this update, you will receive the following error message and will be unable to use the simulator: The com.apple.CoreSimulator.SimRuntime.iOS-17-2 simulator runtime is not available. Domain: com.apple.CoreSimulator.SimError Code: 401 Failure Reason: runtime profile not found using "System" match policy Recovery Suggestion: Download the com.apple.CoreSimulator.SimRuntime.iOS-17-2 simulator runtime from the Xcode To resume using the simulator, please reboot your Mac. After rebooting, check Xcode Preferences → Platforms to ensure that the simulator runtime you would like to use is still installed. If it is missing, use the Get button to download it again. The Xcode 15.3 Release Notes are also updated with this information.

I am testing auto renewing subscriptions for a macOS program in Xcode with a local Storekit file. I have renewals set to occur every minute for testing. I quit the app, and watch renewals appear in the Debug transaction manager window. Each is marked unfinished. When I start the app, I call a function that is supposed to get unfinished transactions and finish them. In one of those "I swore it worked the other day", I am now finding it isn't working. The unfinished transaction remain marked as unfinished. func getUnfinished() async { for await verificationResult in Transaction.unfinished { guard case .verified(let transaction) = verificationResult else { continue } await transaction.finish() } } If I add an AppStore.sync() right before looping on Transaction.unfinished, it works (i.e., cleans up unfinished transactions), but I get an alert I have to click through. do { try await AppStore.sync() } catch { print("DEBUG UNFINISHED: AppStore.sync() failed: \(error)") } Any idea why Transaction.unfinished isn't fetching unfinished transactions for me (without the AppStore.sync)?

It would be helpful if the required token scopes were pre-filled in the URL when clicking the "Create a Token on GitHub" button when signing into a GitHub account in Xcode. FB22632532 https://github.com/feedback-assistant/reports/issues/796

HI, I have a Swift UI app in the mac appstore in the upcoming release we have made lots of changes and it is working fine in debug mode but in production with testflight or direct distribution we are getting the following crash while working in the app. this is happening in the rendering phase. Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libswiftCore.dylib 0x19546f270 swift_unknownObjectRetain + 44 1 libswiftCore.dylib 0x1954bb09c swift_cvw_initWithCopyImpl(swift::OpaqueValue*, swift::OpaqueValue*, swift::TargetMetadata<swift::InProcess> const*) + 280 2 libswiftCore.dylib 0x1958f685c initializeWithCopy for ClosedRange<>.Index + 212 3 VirtualProg 0x104d73958 <deduplicated_symbol> + 56 How can i debug to find out what is causing the issue and fix it?. thanks in advance

Xcore 26.2 run on newly installed macOS 15.7.3 (24G419) crashes when attempting to build assets backtrace

Description Xcode 26.4.1 crashes immediately on launch with a code signature error. The issue exists on macOS 26.4.1 and persists after upgrading to macOS 26.5 (25F5058e) and attempting 26.6 beta. Crash Details: Exception Type: EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid)) Termination Reason: Namespace CODESIGNING, Code 2, Invalid Page Key symbols: dyld3::MachOFile::trieWalk, dyld4::JustInTimeLoader::applyFixups, dyld4::Loader::forEachBindTarget All Steps Tried (All Failed): Fresh reinstall from Mac App Store and .xip from Developer website Multiple sudo xattr -cr + sudo codesign --force --deep --strict --options=runtime --sign - Deleted all Xcode caches, DerivedData, and preferences Tested in a brand new user account (same crash) Downgraded Xcode to older versions macOS remains on 26.4.1 (issue existed here) and upgraded to 26.5 / attempted 26.6 beta — still same crash Refreshed Apple Worldwide Developer Relations certificates Multiple restarts The crash report is identical every time. System Information Model: MacBook Pro (M1 Pro, MacBookPro18,1) macOS: 26.5 (25F5058e) — issue started after upgrade from 26.4.1 Xcode: 26.4.1 (24909.0.3) SIP: Enabled Developer Mode: Enabled Additional Notes Other applications launch normally. This appears to be a system-level compatibility issue introduced in macOS 26.5's stricter code signing validation on mapped files / chained fixups. Request Is there a known workaround? Is Apple preparing a fix in a future macOS 26.5 patch or Xcode update? What additional information would help? Thank you!

Hello everyone, my app A now supports iOS Widget C under the same Xcode project. Now I have another app B under this project, and I hope it can also support this Widget C. What should be done? How should the app group be configured? I have found some solutions: for example, add this key under the info.plist corresponding to app B: NSExtension NSExtensionPointIdentifier com.apple.widgetkit-extension NSExtensionPrincipalClass $(PRODUCT_MODULE_NAME).WidgetEntryView However, when I configured it and started running, not only could I not see the support Widget C, but the screen also went black. Thank you all.

Hello everyone. I need help! I'm using Xcode solely to create an archive of a mobile application created with WinDev Mobile. When everything is working correctly, I simply retrieve the application's generated version from WinDev Mobile, launch the archive creation process, and add a new version to TestFlight! Then I can test the application on the iPhone. The current problem is that the application crashes, without any error message, in a specific use case. Hoping to get some help with this crash, I had the idea to test the application using Xcode. Once launched, a crash occurs if I follow the same process. There's an error message, which I'll paste below. What does this error mean? How can I relate it to my WinDev Mobile code? Have a good day.

I am running Tahoe 26.4.1 on a MacBook Air, M4, 2025. In System Settings, I have an item heading of Software Update Available. Clicking on that brings up "Command Line Tools for Xcode 26.4". The only available choices are to Update Now or Cancel. In the past, I was developing a game, but have quit working on that, and deleted Xcode and Command Line Tools. Wanting the "Command Line Tools ..." line to disappear from System Settings, I called Apple Support, and at their request have followed the steps in "https://developer.apple.com/documentation/xcode/installing-the-command-line-tools" to delete this entry in System Settings, namely the 2 sudo's in that article under the section "Uninstall the command line tools". This did not cause the "Command Line Tools for Xcode 26.4" line in System Settings to disappear (as I was told by Apple support that it would, because I would be deleting the receipt). In Terminal, I did indeed receive a response of "No receipt for 'com.apple.dt.commandlinetools' found at '/'.". I have called developer support, but the individual I spoke with had no useful guidance on how to finish this issue, except to post to the Forum. I would appreciate any guidance on how to delete the "Command Line Tools ..." entry from System Settings.

My app start up has became horrid. It takes 1 minute to open SQLlite database for my rust core. Impossible to work... I have Address Sanitizer, Thread Perf Checker and Thread Sanitizer disabled...

Translated Report (Full Report Below) Process: Xcode [3078] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 26.4.1 (24909.0.3) Build Info: IDEApplication-24909000003000000~2 (17E202) Code Type: ARM-64 (Native) Role: Default Parent Process: launchd [1] Coalition: com.apple.dt.Xcode [1424] User ID: 501 Date/Time: 2026-04-24 17:26:21.8348 +0800 Launch Time: 2026-04-24 17:26:21.7161 +0800 Hardware Model: MacBookPro18,1 OS Version: macOS 26.5 (25F5058e) Release Type: User Crash Reporter Key: 7A149229-7AEE-0654-7878-1A66190C590A Incident Identifier: AC932530-5FCF-45B1-90F3-D26B40150344 Time Awake Since Boot: 3400 seconds System Integrity Protection: enabled Triggered by Thread: 0, Dispatch Queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid)) Exception Subtype: UNKNOWN_0x32 at 0x0000000112948000 Exception Codes: 0x0000000000000032, 0x0000000112948000 Termination Reason: Namespace CODESIGNING, Code 2, Invalid Page

EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid)) Crash Report

Hi there, In the last few days ALL TF builds i has been flagged as Expired. Uploading new builds to TF seems to be successful but we get a 404 on the download link. It doesn't exist! Client side we have seemingly exhausted all our lines of enquiry. All certification seems to be correct and intact, and we can publish to the store. We cannot distribute builds through TF - which is highly problematic and inconvenient. These issues seems to be happening to many developers but I've not seen Apple comment on this yet. https://developer.apple.com/forums/thread/823347 https://developer.apple.com/forums/thread/778597 https://developer.apple.com/forums/thread/778597?answerId=885232022#885232022 I offer this as a sidenote. We transferred an app from this store, successfully to another store. The timing at first seemed linked, but now having seen other reports, it may just have been coincidence. Thankyou for your attention.

Since 26.4 beta 3 I've been having errors after a few hours of using Claude Agent. I get an error stating that I am not authed. If I go into Xcode settings, it still shows I am signed into Claude Agent. I have click sign out and then go through the whole auth process again to start using the agent again. This is on two separate computers. Is there anything I can do to stop this behaviour and stay logged in for longer? It worked fine in 26.3.

I switch between Project / Tests / Breakpoints using top left pane 100s times a day. I also switch to search using CMD-Shift-F. In Xcode 26.4 I have to tap the <> to open menu. Is there a way to bring back the old behavior. Does any of the UX guys who worked on that feature use Xcode on daily basis? This is so bad :(

I have an orphaned asset folder taking up 9.13GB located at: /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/c0d3fd05106683ba0b3680d4d1afec65f098d700.asset It contains SimulatorRuntimeAsset version 18.5 (Build 22F77). Active Version: My current Xcode setup is using version 26.2 (Build 23C54). I checked the plist files in the directory and found what seems to be the cause of the issue: The "Never Collected" Flag: The Info.plist inside the orphaned asset folder explicitly sets the garbage collection behavior to "NeverCollected": <key>__AssetDefaultGarbageCollectionBehavior</key> <string>NeverCollected</string> The Catalog Mismatch: The master catalog file (com_apple_MobileAsset_iOSSimulatorRuntime.xml) in the parent directory only lists the new version (26.2). Because the old version (18.5) is missing from this XML, Xcode and mobileassetd seem to have lost track of it entirely. What I Have Tried (All Failed) Xcode Components: The version 18.5 does not appear in Settings -> Components, so I cannot delete it via the GUI. Simctl: xcrun simctl list runtimes does not list this version. Running xcrun simctl runtime delete 22F77 fails with: "No runtime disk images or bundles found matching '22F77'." Manual Deletion: sudo rm -rf [path] fails with "Operation not permitted", presumably because /System/Library/AssetsV2 is SIP-protected. Third-party Tools: Apps like DevCleaner do not detect this runtime (likely because they only scan ~/Library or /Library, not /System/Library). Has anyone found a way to force the system (perhaps via mobileassetd or a specific xcrun flag) to re-evaluate this folder and respect a deletion request? I am trying to avoid booting into Recovery Mode just to delete a cache file. Any insights on how AssetsV2 handles these "orphaned" files would be appreciated.

Several app developers are struggling with the inability to provide a separate app icons that looks nice on older macOS versions while at the same time provide Icon Composer icons that look great on macOS Tahoe 26. An ability to provide separate icons is super important to those who have app icons that follow the curvature of the default icon borders (as the corner rounding radius is different for Sequia and Tahoe). Take a look at this for example: https://github.com/ghostty-org/ghostty/issues/7564#issuecomment-3042061547 Question: Is there a definitive/recommended way to address this issue? How can a developer add a glass icon variant that looks good on Tahoe and provide a bitmap icon for older macOS versions? Some background info: Prior to Xcode 26 beta 4, one could add an App Icon to Assets to be used as app icon for legacy macOS versions (Sequia and older) and use a new Icon Composer icon (placed in the project root) for macOS Tahoe 26. Enabling "Include all app icon assets" under target settings ensured that older macOS versions would use the old app icons while Tahoe the new Icon Composer glass one. Since Xcode beta 4 this technique no longer works. Xcode instead insists on populating Assets.car with Icon Composer generated variants, disregarding the App Icon provided in Assets. Although the App Icon in Assets makes its way to a .incs file in the app bundle's Contents/Resources folder, but that is not used by macOS anymore and is there for some compatibility purposes. The Assets.car file (which matters) only contains the variants generated by Icon Composer and does not contain the png icons provided in the Assets.

I am facing errors in running ROOT on my M4 Air below is the terminal output can you please help me akshatsharma@akshats-MacBook-Air ~ % root /Users/akshatsharma/Applications/ROOT_v6.36.06/etc/cling/std_darwin.modulemap:73:64: error: header '__type_traits/add_lvalue_reference.h' not found module add_lvalue_reference { header "__type_traits/add_lvalue_reference.h" } ^ input_line_1:1:10: note: submodule of top-level module 'std' implicitly imported here #include <new> ^ Warning in cling::IncrementalParser::CheckABICompatibility(): Failed to extract C++ standard library version. Warning in cling::IncrementalParser::CheckABICompatibility(): Possible C++ standard library mismatch, compiled with _LIBCPP_ABI_VERSION '1' Extraction of runtime standard library version was: '' ------------------------------------------------------------------ | Welcome to ROOT 6.36.06 https://root.cern | | (c) 1995-2025, The ROOT Team; conception: R. Brun, F. Rademakers | | Built for macosxarm64 on Dec 27 2025, 07:23:39 | | From tags/6-36-06@6-36-06 | | With Apple clang version 17.0.0 (clang-1700.6.3.2) | | Try '.help'/'.?', '.demo', '.license', '.credits', '.quit'/'.q' | ------------------------------------------------------------------ root [0] new TBrowser IncrementalExecutor::executeFunction: symbol '_ZN5cling7runtime6gClingE' unresolved while linking [cling interface function]! You are probably missing the definition of cling::runtime::gCling Maybe you need to load the corresponding shared library? root [1] .q akshatsharma@akshats-MacBook-Air ~ % xcode-select --install xcode-select: note: Command line tools are already installed. Use "Software Update" in System Settings or the softwareupdate command line interface to install updates akshatsharma@akshats-MacBook-Air ~ % xcode-select -p /Library/Developer/CommandLineTools akshatsharma@akshats-MacBook-Air ~ % sudo xcode-select --reset akshatsharma@akshats-MacBook-Air ~ % sudo xcodebuild -license accept xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance akshatsharma@akshats-MacBook-Air ~ % unset DYLD_LIBRARY_PATH unset LD_LIBRARY_PATH source /Users/akshatsharma/applications/ROOT_v6.36.06/bin/thisroot.sh root -l /Users/akshatsharma/Applications/ROOT_v6.36.06/etc/cling/std_darwin.modulemap:73:64: error: header '__type_traits/add_lvalue_reference.h' not found module add_lvalue_reference { header "__type_traits/add_lvalue_reference.h" } ^ input_line_1:1:10: note: submodule of top-level module 'std' implicitly imported here #include <new> ^ Warning in cling::IncrementalParser::CheckABICompatibility(): Failed to extract C++ standard library version. Warning in cling::IncrementalParser::CheckABICompatibility(): Possible C++ standard library mismatch, compiled with _LIBCPP_ABI_VERSION '1' Extraction of runtime standard library version was: '' root [0] new TBrowser IncrementalExecutor::executeFunction: symbol '_ZN5cling7runtime6gClingE' unresolved while linking [cling interface function]! You are probably missing the definition of cling::runtime::gCling Maybe you need to load the corresponding shared library? root

Good day! When your project have total 887 or more SPM local targets and then you try to build it, xcodebuild will be crash. Crash log: SWBBuildService-2025-08-11-151103.ips Thread 2 Crashed:: Dispatch queue: com.apple.root.default-qos.cooperative 0 libxpc.dylib 0x197c4826c _availability_version_check + 8 1 libswiftCore.dylib 0x1a9b44428 __isPlatformVersionAtLeast + 92 2 libswiftCore.dylib 0x1a9a6e054 _swift_allocObject_ + 1100 3 SWBMacro 0x104a9c408 specialized _ArrayBuffer._consumeAndCreateNew(bufferIsUnique:minimumCapacity:growForAppend:) + 116 4 SWBMacro 0x104a97b58 specialized Array.append<A>(contentsOf:) + 116 5 SWBMacro 0x104a954e8 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 160 6 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 7 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 8 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 9 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 10 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 But if you try to build Package.swift via swift build command, it works. Here you can open sample project: Just Package.swift with SPM 900 targets Open Package.swift via Xcode 26 any beta and try to build Xcode workspace with SPM 900 targets Open MyApp.xcworkspace and try to build You can also make by self the Package.swift (also make required directories for SPM): // swift-tools-version: 5.9 import PackageDescription // let count = 800 // no crash let count = 900 // crash let targetsNames = (1...count).map { "Pkg1Target\($0)" } let targets = targetsNames.map { Target.target(name: $0) } let package = Package( name: "Pkg1TargetLibrary", platforms: [.iOS(.v16)], products: [ .library(name: "Pkg1TargetLibrary", targets: targets.map(\.name)), ], targets: targets )

FB19249805 Main: The option to open files in New Window Tab doesn't appear anywhere in either Preferences or the contextual menu on clicking the files in the project (unlike previous Xcode versions). Only the option to open in New Tab is available (which is useless). This BREAKS EXISTING WORKFLOWS that have been established through years for countless developers. I can only see the option to open in New Tab, which breaks all existing workflows and habits. This results in an astonishing blow to productivity. Dear Xcode team: Please restore this option immediately! Additional details: Several years ago (I've been using Xcode since version 2), Xcode renamed the normal tabs into "Window Tabs" and introduced new "Tabs". The new "Tabs" proved to be a useless and counterproductive option for the following reasons: -They cannot be used in Behaviors. (Only Window Tabs can be, and many workflows have been built around this.) -It takes much longer to load a file into a Tab than into a Window Tab (where files are loaded nearly instantly). -Navigators and Inspectors cannot be customized for individual Tabs (only for Window Tabs). -Using both Tabs and Window Tabs is not an option, as it adds another tab bar that eats an enormous part of screen real estate without providing any benefits. Fortunately, we didn't have to use Tabs and could just disable them into oblivion where they belong. Now, in Xcode 26, the option to open files in new Window Tabs is gone. Really, I can only classify it as intentional sabotage. Many years of my Xcode habits and workflows are based on opening files in New Window Tabs via the Preferences > Navigation > With Option option. Or via the contextual menu. Now this option is gone. I'm sure there are plenty of other developers in the same situation. Please reenable the option to open in New Window Tabs. Thank you for your attention to this matter!

Previews seemed to be working okay. However, I wanted to test out some changes inside of a package that I'm working on for work, but in a lighter project since in our main project (where I have the package pulled in locally for now) is just too big to have the previews render in a decent amount of time. So, I opened a small project that was already importing that package and was set to 'Up to Next Major', but I switched that to 'branch' and added my branch. This is the second time I've done that and it causes Xcode to freak out in terms of the previews. This is the code I have: import SwiftUI extension EnvironmentValues { @Entry var trailingDescriptionColorToken: Color = .secondary } extension View { func updateTrailingDescriptionColor(to colorToken: Color, when trigger: Bool) -> some View { environment(\.trailingDescriptionColorToken, trigger ? colorToken : .secondary) } } // MARK: - ListItemDescription public struct ListItemDescription: View { @Environment(\.trailingDescriptionColorToken) var trailingDescriptionColorToken let description: String init(_ description: String) { self.description = description } public var body: some View { Text(description) .font(.caption) .foregroundStyle(trailingDescriptionColorToken) } } struct ContentView: View { @State private var isError = false var body: some View { VStack { Button("Error Trigger") { isError.toggle() } ListItemDescription("Description") .updateTrailingDescriptionColor(to: .red, when: isError) } .padding() } } #Preview { ContentView() } As soon as I tap the button to toggle the isError state property, that causes the preview canvas to indefinitely load and spin eventually leading to a crash. This is infuriating as I've just wasted a ton of time at work trying to figure out what's going on. Xcode and SPM is so fragile and delicate that at this point I feel like if I breathe on it wrong it'll break. I'm not sure what fixed it last time. Nothing in Xcode makes sense anymore. How to I resolve this please?